From cb7c9035948f292e2c3d8927364e6ecb975d480c Mon Sep 17 00:00:00 2001 From: Holger Knust Date: Sat, 15 Aug 2020 05:20:03 -0400 Subject: [PATCH] gtkassistant: Minor docstring wording changes Changed the wording to improve the clarity of the documentation. Fixed grammar issue ("spllited") --- gtk/gtkassistant.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/gtk/gtkassistant.c b/gtk/gtkassistant.c index b776fbabba..ebe6b8e4f3 100644 --- a/gtk/gtkassistant.c +++ b/gtk/gtkassistant.c @@ -27,15 +27,15 @@ * @Title: GtkAssistant * * A #GtkAssistant is a widget used to represent a generally complex - * operation splitted in several steps, guiding the user through its - * pages and controlling the page flow to collect the necessary data. + * operation split up into several steps. Each step consists of one or more + * pages. GtkAssistant guides the user through the pages, and controls + * the page flow to collect the data needed for the operation. * - * The design of GtkAssistant is that it controls what buttons to show - * and to make sensitive, based on what it knows about the page sequence - * and the [type][GtkAssistantPageType] of each page, - * in addition to state information like the page + * GtkAssistant handles which buttons to show and to make sensitive based + * on page sequence knowledge and the [type][GtkAssistantPageType] + * of each page in addition to state information like the * [completion][gtk-assistant-set-page-complete] - * and [committed][gtk-assistant-commit] status. + * and [committed][gtk-assistant-commit] page statuses. * * If you have a case that doesn’t quite fit in #GtkAssistants way of * handling buttons, you can use the #GTK_ASSISTANT_PAGE_CUSTOM page -- 2.30.2